Table of Contents
This chapter provides information on managing asynchronous jobs and on defining and managing schedules.
A job is defined as any asynchronous task. On a Data ONTAP 10.0 system, jobs are typically long-running volume operations such as copy, move, and mirror. Jobs are placed into a job queue and run when resources are available. If a job is consuming too many system resources, you can stop it or pause it until there is less demand on the system.
The Data ONTAP 10.0 system defines the following types of jobs:
A server-affiliated job is queued by the management framework to a specific node to be run.
A cluster-affiliated job is queued by the management framework to any node in the cluster to be run.
A private job is specific to a node and does not use the replicated database (RDB) or any other cluster mechanism. The commands that manage private jobs require the advanced privilege level or higher.
Many tasks—for instance, volume snapshots and mirror replications—can be configured to run on specified schedules. Schedules that run at specific times are known as cron schedules because of their similarity to UNIX cron schedules; schedules that run at intervals are known as interval schedules. You can define cron schedules by using the job schedule cron commands and interval schedules by using the job schedule interval commands.